Upgrading the BootROM

The ExtremeSwitching series switches have a two-stage bootROM. The first stage, called bootstrap, does basic initialization of the switch processor and loads one of two second-stage bootloaders (called primary and secondary).

If the switch does not boot properly, both the bootstrap and the bootloader allow you to access the boot options using the CLI.

If necessary, the bootloader can be updated after the switch has booted, using TFTP. You can upgrade the bootROM from a TFTP server on the network after the switch has booted and only when asked to do so by an Extreme Networks technical representative. For information about loading an image to a TFTP server and verifying which virtual router connects to your TFTP server, see Installing a Core Image.

To download to a single stacking node, you need to specify the slot parameter:
download bootrom [[ipaddress | hostname] filename {{vr} vrname} {block-size block_size}] {slot slotid} {install} {reboot}}
Note
User-created VRs are supported only on the platforms listed for this feature in the Switch Engine v33.1.1 Licensing Guide document.
For ExtremeSwitching Universal switches (except 4120, 5720, 7520, and 7720 series switches, which use ONIE), you can upgrade the bootROM with the version packaged in the ExtremeXOS .xos image file using the from-exos option: This command uses the bootROM image from the booted ExtremeXOS image. After reboot, the new bootROM image is used.
install bootrom [from-image | fname | local-file] {slot slot-number} {reboot}
When you download and install new version of ExtremeXOS image, the system automatically compares the currently installed bootROM image against the bootROM image contained in the new ExtremeXOS image. If the installed version is older version, the system automatically upgrades bootROM to the version contained in new ExtremeXOS image.

To view which version bootROM is on each partition, use the show version {detail | process name | images {partition partition} command.

If the bootROM image is invalid, this command shows 0.0.0.0. If the primary bootROM is invalid, the bootROM upgrade will be canceled. To fix this, re-install the bootROM on the primary partition.